Mobile payment management

ABSTRACT

A method for managing mobile payments in a mobile phone. The method includes receiving data associated with a plurality of issuer specific payment services at a mobile phone, selecting one of the issuer specific payment services, and conducting a transaction using the phone.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a non-provisional of and claims priority to U.S. provisional patent application No. 60/884,212, filed on Jan. 9, 2007 and U.S. provisional patent application No. 60/884,290, filed on Jan. 10, 2007, both of which are herein incorporated by reference in their entirety for all purposes.

This application is also related to U.S. patent application Ser. No. ______, entitled “Mobile Phone Payment With Disabling Feature” (Attorney Docket No. 16222U-038330US), U.S. patent application Ser. No. ______, entitled “Mobile Phone Payment Process including Threshold Indicator” (Attorney Docket No. 16222U-038340US), and U.S. patent application Ser. No. ______, entitled “Contactless Transaction” (Attorney Docket No. 16222U-038310US) all of which are being filed on the same day as the present application. These applications are herein incorporated by reference in their entirety for all purposes.

BACKGROUND

People of all ages around the world use a mobile phone as an essential component of their day. In some parts of the world they are the primary communication device, but mobile phones are more than just communication devices. They are truly multi-functional, providing the consumer with the capability to not only place and receive phone calls but also to take photos, send text messages, listen to music, surf the Web, and even watch movies.

Consumer demand for all-purpose multi-functional mobile phones is increasing. Technology that supports a mobile payments infrastructure is emerging (i.e., contactless payment acceptance infrastructure, NFC-enabled mobile phones, and robust mobile networks). The mobile phone has the potential to enhance the security and convenience of using a payment product as well as introduce payment products to parts of the world that don't currently have a support infrastructure for traditional payment products.

Consumers are interested in mobile payments and better ways to conduct transactions using mobile phones and better ways to manage the payment process are needed.

Also, in some cases, a consumer may have two or more payment cards (e.g., credit cards) and may want to use the account numbers associated with those payment cards using his or her phone. The different issuers for those credit cards may have different payment services that can be provided with those cards. It would be desirable to allow a user to use the different payment services offered by such issuers on a single phone.

Embodiments of the invention address these and other problems individually and collectively.

BRIEF SUMMARY

Embodiments of the invention are directed to improved consumer mobile phone payment systems and methods.

One embodiment of the invention is directed to a method. The method comprises receiving data associated with a plurality of issuer specific payment services at a mobile phone; entering a selection of one of the issuer specific payment services as a default service; and conducting a transaction using the mobile phone using the one selected issuer specific payment service.

Another embodiment of the invention is directed to a computer readable medium comprising code for receiving data associated with a plurality of issuer specific payment services at a mobile phone; code for entering a selection of one of the issuer specific payment services as a default service; and code for conducting a transaction using the mobile phone using the one selected issuer specific payment service.

Another embodiment of the invention is directed to a phone comprising: a processor; a memory operatively coupled to the processor, the memory comprising code for receiving data associated with a plurality of issuer specific payment services at a mobile phone, code for entering a selection of one of the issuer specific payment services as a default service, and code for conducting a transaction using the mobile phone using the one issuer specific payment service; a display operatively coupled to the processor; and an antenna operatively coupled to the processor.

Another embodiment of the invention is directed to a method comprising: sending data associated with a plurality of issuer specific payment services to a mobile phone comprising a contactless element, which is capable of allowing the phone to communicate contactlessly with a contactless reader in a point of sale terminal; and sending a plurality of messages from the plurality of issuers to the mobile phone.

Another embodiment of the invention is directed to a computer readable medium comprising code for sending data associated with a plurality of issuer specific payment services to a mobile phone comprising a contactless element, which is capable of allowing the phone to communicate contactlessly with a contactless reader in a point of sale terminal; and code for sending a plurality of messages from the plurality of issuers to the mobile phone.

These and other embodiments of the invention are described in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram of a system according to an embodiment of the invention.

FIG. 2 shows screen shots on a phone display illustrating a configuration process.

FIG. 3 shows screen shots on a phone illustrating a payment process.

FIGS. 4-6 show various screen shots on a phone display with transaction messages.

FIGS. 7-8 show various screen shots on a phone display for balance inquiries.

FIGS. 9(a)-9(b) show various screen shots on a phone display for payment reminders.

FIGS. 10, 11(a), and 11(b) show screenshots associated with balance alerts.

FIG. 12 shows a screen shot indicating that an account is blocked due to suspicious activity.

FIG. 13 shows screen shots illustrating discounts.

FIGS. 14(a) and 14(b) shows screen shots illustrating different issuer specific mobile payment applications that a consumer can select from, and a subsequent screen shot illustrating that a specific mobile payment application has become a default application.

FIG. 15 shows screen shots associated with the selection of an issuer specific mobile payment application as a default application.

FIG. 16 shows a block diagram of a computer apparatus.

FIG. 17 shows a block diagram of a mobile phone with a contactless element.

DETAILED DESCRIPTION

I. Mobile Transaction Systems

Embodiments of the invention combine payment functions with a range of value-added applications and features, such as coupons, personalization, and account management. Embodiments of the invention make it easy for issuers and mobile operators to offer convenient new services to consumers via mobile phones.

Some features of embodiments of the invention include the following:

Payment for telephone services (either prepaid or postpaid): Embodiments of the invention allow a consumer to pay for phone services using a payment application on the consumer's phone.

Contactless payment at the point of sale: Using embodiments of the invention, consumers can easily and quickly use their phone in lieu of a card for payment at merchant locations.

Remote payment: Using embodiments of the invention, a consumer can use his or her mobile phone to pay for goods and services for any card-not-present type of transaction. To use remote payment, the consumer can register his or her payment account number with a mobile operator and then the mobile operator links the consumer's payment account number to the mobile phone number. Whenever the consumer conducts a card-not-present type of transaction (e.g., mail order, telephone order, or Internet purchase), the consumer can provide his or her registered mobile phone number (rather than his or her payment account details) to make the purchase. Mobile money transfers can also take place remotely, but these transactions are unique because they involve the transfer of funds rather than purchases.

Service providers can supply the system's payment and value-added functions via SMS messages (or other messaging protocol) over a mobile network to the consumer's mobile phone. Examples of payment functions include proximity payment, remote payment, and mobile money transfer. Examples of value-added functions include offers, authentication, and top-up of minutes on the mobile phone.

FIG. 1 shows a system according to an embodiment of the invention. Referring to FIG. 1, the participants in embodiments of the invention can include traditional payment services participants such issuers 14, merchants 16, and consumers 10. Other participants also include a mobile operator 26 and mobile service providers such as a messaging service provider 20, a directory services provider 22, and an OTA (over the air) service provider 24.

The system may also comprise a number of specific components. Examples of such components include an offer engine 18, a messaging gateway 20(a), a directory services engine 22(a), and a service activation system 24(a).

The system may also comprise a mobile phone 10(a), which can include mobile phone components such as an NFC communications element 10(a)-1 (near field communications element; which is an example of a contactless element), a secure element comprising a payment application 10(a)-2, and resident applications 10(a)-3 including one or more mobile applications 10(a)-3′ and one or more download managers 10(a)-3″.

Messages may pass between the components illustrated in FIG. 1. Reference number 2 shows arrows for offer management messages, reference number 4 shows arrows for service activation messages, reference number 6 shows arrows for directory service messages, and reference number 8 shows arrows for account management messages.

The various components below are described in further detail below.

II. Payment Service Types and Value Added Services

Embodiments of the invention may facilitate at least three types of payment protocols. The first type may include proximity payment (i.e., contactless payment) for face-to-face payments at a merchant's place of business. The second type may include remote payment for payments taking place in an e-commerce environment or other card-not-present situations. The third type may include mobile money transfers (i.e., person-to-person payment) for transferring funds from one person to another for personal, rather than business, use.

Proximity payment offers the same functionality as conventional contactless card transaction processing, but instead of using a contactless card, the consumer presents a mobile phone containing a payment application to a point of sale (POS) device in a merchant's place of business. The NFC-enabled phone emulates a contactless card and uses the same communication standards. The POS device is the same as those used for contactless cards and the payment application interacts with the POS device in the same way a contactless card does. Payment is initiated via a mobile phone rather than a card, but is otherwise identical to contactless transaction processing.

The payment application that is used in a phone 10(a) according to an embodiment of the invention can support at least two different proximity payment configurations. The first configuration is “always-on.” When the payment configuration is in always on mode, the default payment application 10(a)-2 is always active so that the consumer can initiate a transaction by waving the phone 10(a) in front of the POS device without having to select the pay function. The second configuration is “manual.” When the payment configuration is in manual mode, the consumer 10 can access the payment application 10(a)-2 and select the pay function to make the proximity payment. During this process the consumer 10 can also select the account to use for payment. The issuer 14 can specify which of these configurations, or issuer specific payment service that is associated with the account, is the default and can also specify whether the consumer has the option of choosing a default payment configuration. The proximity payment functionality can be compatible with Visa Contactless Payment Specification (VCPS) 2.0.2. Embodiments of the invention also allow more than one payment application to reside in the secure element and for one of the payment applications to be selected as a default.

Remote payment makes it possible for consumers to use their mobile phone to initiate and authenticate card-not-present transactions between a consumer and a merchant. Remote payments take place over the mobile network and do not involve interacting with a POS device. Remote payment transactions are based on mobile phone numbers instead of account numbers so no financial information is sent over the mobile network. Card-not-present transactions include Internet, call center, and automated services such as interactive voice response (IVR) transactions, as well as face-to-face interactions. Remote payments can use the consumer's registered mobile phone 10(a) as an authentication channel. To use the remote payments function, consumers may register their mobile phone number with a directory service provider 22 or other entity and may link it to an account number so that they can use the registered phone number for payment.

A mobile money transfer refers to a transaction between two individuals. Mobile money transfer allows a cardholder or consumer to transfer money from his or her card or account to another card or account using a mobile phone 10(a). It enables consumers to easily send money to an individual via a mobile phone over the mobile network for international remittances and domestic person-to-person money transfers. Consumers can use mobile money transfer to pay a friend or another individual (who is not a merchant) for services.

Mobile money transfers can rely on aliases instead of account information to transfer funds, so no financial information is sent over the mobile network. Consumers who want to send money can register their account and link it to their mobile phone number. They can also designate the recipients and assign an alias to them. Recipients can register in the service but are not required to do so to receive the funds that are sent to them.

Embodiments of the invention may also provide for a number of value added features including offers, authentication for security purposes, account management, and top-up of mobile phone minutes.

An offer can refer to a coupon, discount, or promotion that an issuer, merchant, or a payment processing organization such as Visa sends to the mobile application on the consumer's mobile phone. The consumer can use the mobile application to redeem the offer.

The offer feature can include at least three elements. The three elements include the offer engine 18 that the merchant 16 or issuer 14 uses to define the offer, the offer message format that ensures delivery to the mobile application (the offer message format can be Visa Mobile Data Format (VMDF)), and the mobile application 10(a) that the offers are sent to. The consumer uses the mobile application 10(a) to manage the offer and to redeem it at a merchant's POS device.

Consumers register (opt-in) with their issuer to receive offers. To send an offer, the merchant or issuer can define the offer and submit it to a payment processing organization such as Visa for review and approval. After the offer is approved, it is entered into the offer engine 18 and is scheduled for delivery to the consumers 10 who have opted-in to receive it. The offer engine 18 formats the offer in a suitable message format and delivers it via SMS or some other mobile channel to the mobile application 10(a)-3 on the consumer's mobile phone 10(a).

The consumer's offers can be delivered to the mobile application 10(a)-3 separate from other messages and can be presented in a defined and branded format. The mobile application 10(a)-3 integrates offer delivery and management with point-of-sale payment. It enables consumers to view, manage, and redeem the offers that they receive. The application 10(a)-3 supports some automated offer management, such as delete on expiry. The offers can include a bar code or promotional code that the merchant scans or enters at the time of purchase. When redeeming offers at a merchant's establishment the consumer can use the mobile phone's proximity payment functionality.

Authentication provides a mechanism for the issuer to request information from the mobile phone that makes it possible for the issuer to confirm that the phone, and the consumer, is indeed what and who they claim to be. It enables all parties in an e-commerce transaction to transmit confidential and correct payment data, and provides authentication that the buyer is an authorized user of a particular account. Both mobile remote payment and mobile money transfer features use payment authentication capabilities.

The top-up feature enables a mobile phone to automate the purchase of minutes on a pre-paid phone. This service is a specific implementation of the remote payment feature. It uses the same mechanism as the remote payments service in that the consumer is purchasing minutes from a mobile operator.

III. Account Management

Account management services include the mobile management of payment account profiles and transactions, ranging from conventional mobile banking to new mobile account management tools. Account management services can be linked to an issuer-specific payment service and can be offered as an extension of the issuer's existing account management services. The mobile payment account management feature can integrate with existing issuer bank systems as well as any future account management service provider, whether it is a bank or another third party.

Each issuer 14 can decide what account management features are available to the consumer. Consumers 10 can use the mobile application 10(a)-3′ to request current account balances, receive payment-applied notices and transaction receipts, and configure and receive balance alerts, transaction alerts, and payment reminders. When account management services are available to the consumer 10, the consumer 10 can configure the features to deliver account information based on consumer criteria. For example, the consumer can request to receive an alert when his or her account balance reaches a specified threshold.

The mobile payment system uses messaging to support account management services. The messaging system formats the message and sends it via the mobile operator's network 26. Consumers 10 send messages requesting account management services and the issuer 14 or merchant 16 send messages in response.

The following table lists the account management messages that are sent from the mobile application 10(a)-3′ on the consumer's mobile phone 10(a) to the issuer 14 or merchant 16 and from the issuer 14 or merchant 16 to the mobile application 10(a)-3′ on the mobile phone 10(a).

Message Sent From To Balance alert configuration request Consumer Issuer Balance inquiry request via mobile Payment reminder configuration request application Transaction alert configuration request Balance alert configuration response Issuer Consumer Balance alert via mobile Balance inquiry response application Payment applied Payment reminder configuration response Payment reminder Transaction alert configuration response Transaction alert Transaction failure receipt Merchant Consumer Transaction success receipt via mobile application

The issuer 14 is traditionally responsible for acquiring, registering, and supporting consumer payment accounts. In the mobile transaction system, in addition to handling the payment accounts, the issuer 14 also has the option of supporting account management and offer management features. These account management and offer management features may be features of an “issuer-specific payment service.” Furthermore, because payment account activation can occur after the consumer 10 has acquired the mobile phone 10(a), the issuer's traditional card issuance processes can migrate to an OTA service activation environment.

The merchant 16 accepts payment with a payment account in both brick-and-mortar and e-commerce settings. The merchant 16 can also use the mobile payment system to issue offers to the mobile customer base, which can range from a targeted subset to the entire set of account holders.

The messaging service provider 20 provides the message interfaces between the consumer's mobile phone 10(a) and the other providers. This provider operates the messaging gateway 20(a) and related systems.

The OTA service provider 24 manages the secure element 10(a)-2 on the mobile device 10(a), including provisioning secure element applications.

The directory services provider 22 supplies support for remote payment and mobile money transfer transactions that use an alias associated with a registered consumer 10 to route to relevant account information.

The consumer 10 uses a mobile phone 10(a) to access the mobile payment and value-added services. The consumer 10 requests the downloading and personalization of any applications onto the mobile phone 10(a).

The mobile operator 26 provides and provisions the mobile network, including the data services needed to support the above-described services. The mobile operator 26 also typically selects the mobile phones that its network supports and the applications that function on these mobile phones. It also sends messages to and receives messages from the mobile phone 10(a).

Messaging enables the interaction between disparate platform participants. Messages support account management, basic offers, and service activation as well as directory services for remote payments and mobile money transfer.

Some embodiments of the invention are directed to using various combinations of messages to manage a consumer's payment accounts. One embodiment of the invention comprises receiving an account balance inquiry response message using a mobile phone. The mobile phone comprises a contactless element that is configured to communicate with a contactless reader in a point of sale terminal. The account balance inquiry response message provides an account balance for an account associated with the mobile phone, the mobile phone being operated by a consumer. The method also includes receiving a transaction alert message using the mobile phone, wherein the transaction alert informs the consumer that a transaction has occurred using the account, and also receiving an offer message, wherein the offer message provides a benefit for the consumer if the consumer uses the mobile phone to a conduct predetermined transaction. Such message may be received by the mobile phone 10(a) and may be displayed by the mobile phone 10(a).

The mobile operator 26 or any other suitable entity may correspondingly send a balance inquiry response message, transaction alert message, and an offer message to the mobile phone. The mobile operator 26 may operate a communications server comprising a processor, and a computer readable medium operatively coupled to the processor. The computer readable medium can comprise code for sending the various messages to the mobile phone 10(a).

The messaging service provider 20 formats the messages the issuer 14, merchant 16, and other service providers send and delivers them to the mobile application 10(a)-3′ on the mobile phone 10 via the mobile network. It also formats and delivers account management messages the consumer 10 sends via the mobile application 10(a)-3′ on the mobile phone 10 to the issuer 14 and merchant 16.

The basic protocol followed for messages sent to and from the mobile application 10(a)-3′ can be the Visa Mobile Data Format (VMDF). All messages can be in VMDF format by the time they reach the messaging gateway 20(a) to ensure that they are delivered to the mobile application 10(a)-3′. The VMDF is not SMS-specific. It encompasses the use of any text or binary data provided for the application over the network and for local storage purposes.

The messaging service provider 20 operates the messaging gateway 20(a), which supplies a unified message interface between other providers and participants and the consumer's mobile phone 10(a). The messaging gateway 20(a) supports at least three features. The first feature is an alert API which facilitates the transfer of messages both to and from the mobile application 10(a)-3′ on the consumer's mobile phone 10(a). The second is a reporting Web interface which allows issuers 14, merchants 16, and a payment processing organization such as Visa to monitor the relevant traffic to and from the consumer's mobile phone applications. The third is a testing hub that is an interface that allows participants to send messages to and receive messages from a virtual mobile application to test the readiness of their systems. The testing hub supports both account management and offer messaging.

The offer engine 18 is the system that is responsible for managing offers. Its capability may range from being a simple user interface (UI) through which merchants 16 can define offers to a sophisticated database marketing system that can target offers to consumers based on a wide range of demographic and behavioral data. In addition, the messaging gateway 20(a) supports an offers Web interface, which acts as the offer engine. It is a basic Web-based UI through which merchants 16 can define simple offers for delivery to all consumers 10.

The process of enabling a mobile phone is called “service activation,” because it constitutes activation on the mobile phone. Service activation can be used to provision the payment application 10(a)-2′, the mobile application 10(a)-3′, a service activation application, account information, and data (such as data relating to an issuer specific payment application) onto the mobile phone. Without service activation, such applications can only be issued if the secure element, and in many cases the mobile phone itself, is personalized before the consumer takes possession of it. While service activation is a general term for this activation that could theoretically take place via multiple channels or means, embodiments of the invention are preferably focused on the over-the-air (OTA) provisioning of the payment application to a secure element 10(a)-2 on a mobile phone 10 via the mobile network. OTA service activation allows the issuer 14 to securely enable the phone 10(a) remotely with secure payment and account data without requiring the consumer to visit its bank or a retail outlet.

The OTA service provider 24 operates and manages the OTA service activation system 24(a). The OTA service activation system 24(a) provides personalization and issuance functionality as well as day-to-day management of the consumer's secure element applications. A feature of the OTA service activation system 24(a) is the provisioning and personalization of the secure element applications using the mobile operator's network. Furthermore, the OTA service provider 24 uses this system 24(a) to manage the secure elements deployed in the field after they are personalized. This is a desirable feature for managing payment accounts. Compromised accounts can be locked and unlocked and the platform can be removed OTA. The OTA service activation system 24(a) provides information to the mobile phone OTA for loading, installing, and personalizing the software on the phone, locking and unlocking the applications on the phone, and removing applications from the phone. It communicates with the download manager 10(a)-3″ on the phone to carry out OTA activities.

OTA service activation also provides remote control of mobile phones for corporate branding, offers, and messaging configuration and programming of new services without user intervention. It uses OTA technology to communicate with the SIM or NFC chip without physical access to the phone 10(a). New services can be securely downloaded without operator re-issuance of the mobile phone 10(a).

Directory services are used to support mobile money transfers and remote payments as well as value-added services such as advanced offers (in a future release of the platform), authentication, and top-up. Directory service is desirable for transactions that use an alias associated with a registered consumer to route to other information. It determines who the consumer is and then routes the relevant consumer information to the issuer.

For mobile money transfers, an alias can be used to identify and/or contact the recipient of the money transfer. Typically, the directory allows senders to use an alias that is more convenient or human-friendly (like a mobile number) than an account number. In money transfer transactions, aliases/directories also allow greater privacy between the sender and the recipient. Each party's bank can retain respective personal information belonging to the sender and recipient securely, without the need for the sender and recipient or cardholder and merchant 16 to share any personal information with each other to conduct the transaction.

The mobile phone 10(a) is the conduit between the service providers and the consumer 10. The mobile phone 10(a) includes a number of distinct features. The first feature is NFC (near field communications) radio capability which offers card emulation mode to enable proximity payment. It includes an antenna to communicate with the merchant's contactless POS device. A second feature is a secure element form factor to securely hold the payment application. A third feature is an existing mobile application space with a mobile application 10(a)-3′ and a download manager 10(a)-3″.

The mobile phone 10(a) can: initiate payment transactions, receive data relating to issuer specific payment services, present the issuer specific payment services to a consumer for selection, receive offers from issuers and merchants and display them; receive account management information from issuers 14 and display it in the mobile application; and communicate with the OTA service activation system 24(a) for OTA activities.

To enable mobile payments, the secure element 10(a)-2 provides the following capabilities. It can provide secure storage to protect sensitive data related to mobile payments. This includes private keys associated with the phone and consumer, public keys, and credentials associated with issuers and back end systems. It can also provide the ability to securely store consumer-specific personal information associated with mobile payments such as a credit/debit card's PAN (personal account number). It can also provide cryptographic functions to support secure payment protocols, data integrity, and confidentiality. This includes support for encryption/decryption, signature verification, and authentication of the secure SMS messages received from the issuer, service activation system, and other back end systems. It can also provide secure deployment and execution environment for the mobile payment application 10(a)-3″.

It is understood that although the specific examples described herein include the use of a secure element and a payment application within the secure element, and a mobile application outside of the secure element, embodiments of the invention are not limited to this. For example, the functions of the payment application and the mobile application can be combined into one application in any suitable logical section of hardware in the phone.

The secure element 10(a)-2 can be in one of the following forms: Embedded hardware: This is a tamper-proof hardware smart card with contactless capability that is integrated tightly with the mobile phone. Removable Universal Subscriber Identity Module (USIM): The secure element can be integrated with a USIM card that provides smart card functionality. In this case, the contactless capability is separate. Removable Secure Digital (SD) card: A smart card provides a secure programmable environment. Applications and mobile payments-specific security information are provisioned on the smart card. The communication to the secure element on the smart card uses APDU commands.

The secure element can also provide an integrated NFC capability that supports the ISO 14443 standard. The NFC capability provides support for peer-to-peer, reader/writer, and card emulation modes.

The payment application 10(a)-2′ is securely stored on the mobile phone's secure element 10(a)-2 and is used to conduct payment transactions. It may include one of two Java card applications—the Visa Smart Debit/Credit (VSDC) card specification applets integrated with the Proximity Payment System Environment (PPSE). The VSDC application is the payment application; the PPSE application is the directory application that stores the details of the payment application. This is the same application that is used for commercially available Visa payWave contactless payment cards. The VPA currently uses contactless specification VCPS 2.0.2. The current version of the GlobalPlatform applet is version 2.7.

The payment application 10(a)-2 contains both payment functionality and the issuer/cardholder personalization data. The payment application 10(a)-2 is provisioned and personalized on the secure element 10(a)-2 with data the issuer 14 sends OTA through the service activation system 24(a). The service activation system 24(a) channels OTA provisioning, initialization, and personalization commands (based on the issuer's specification) from the service activation system to the payment application 10(a)-2. A personalized instance of payment application 10(a)-2′ can be locked, unlocked, and removed from the secure element 10(a) using OTA commands that the issuer 14 initiates through the service activation system 24(a).

To initiate mobile proximity payments, a specific payment application 10(a)-2′ (represented by a unique application identifier (AID)) is associated with a specific mobile application 10(a)-3′, which links the consumer experience with the mobile proximity mechanism. In addition, the secure element 10(a)-2 can have a specific payment application 10(a)-2′ configured as the default for proximity payments.

The payment application 10(a)-2′ interfaces with a contactless proximity modem in either manual or automatic mode. When the mobile phone 10(a) comes into proximity of a contactless POS device, the payment application 10(a)-2′ is automatically notified if the application is configured in an automatic payment mode. In manual mode, communication with the POS is initiated by the consumer 10 via the mobile application 10(a)-3′.

The mobile application 10(a)-3 includes the user interface. It contains the user interface for payment, account management, offer management and redemption, and setting preferences. The mobile application 10(a)-3 is a J2 ME/MIDP 2.0 application (MIDIet). Mobile Information Device Profile (MIDP) is the specification published for the use of Java on embedded devices such as mobile phones. Each mobile application 10(a)-3 can be customized and configured for a specific issuer and is associated with a specific payment application instance.

The customization and configuration process can include the receipt of data associated with the issuer specific payment application instance, which may be linked to an issuer specific payment service. In embodiments of the invention, there may be many different issuer specific payment application instances linked to different issuer specific payment services. The different issuer specific payment services may have different sets of features. For example, one issuer may provide offer messages, and does not provide transaction alert messages. Another issuer may provide transaction alert messages, but does not provide offer messages. In embodiments of the invention, the consumer 10 may select one issuer specific payment service as a default service for use with his phone 10(a), and then may use the phone 10(a) and the selected issuer specific payment service to conduct transactions such as payment transactions. The issuer specific payment services may include specific management services and payment functions.

The mobile application 10(a)-3′ can be OTA provisioned, activated, and configured according to the issuer's specifications on the mobile phone 10(a) during service activation and initialization. Once configured, an application instance appears as an entry in the phone's main menu folder for mobile payments and other financial applications. There can be more than one application instance on the menu based on the number of instances of the mobile application that have been activated, provisioned, and configured on the phone 10(a).

The user interface can include a splash page that welcomes the consumer to the application, a main menu page of all the features the issuer is supporting, payment-related pages, and the detail pages of the features that the issuer is supporting. The issuer 14 can customize certain visual elements of the user interface, such as providing a logo and product name and customizing the splash screen.

The mobile application 10(a)-3′ can use APDU commands to interface with the corresponding payment application 10(a)-2′ to enable proximity payments and provide a secure storage of credentials associated with mobile payments and the consumer 10.

The download manager 10(a)-3″ can be a MIDIet that resides on the mobile phone 10(a) (but not on the secure element 10(a)-2). It is the interface between the service activation system 24(a) and the secure element 10(a)-2. It is responsible for initial provisioning, service activation, initialization, management (including locking and unlocking of the mobile application 10(a)-3′), and configuration of the mobile application 10(a)-3′, the secure element 10(a)-2, and the payment application 10(a)-2′. The download manager 10(a)-3″ interfaces with the service activation system 24(a) (as part of the backend systems) and local device management and provisioning agent on the mobile phone 10(a) for these functions.

IV. Mobile Payment Processes

A number of exemplary payment processes can be described with reference to FIGS. 2-3.

Referring to FIG. 2, a consumer can select whether a proximity payment feature is automatic (always on), manual with no password, or manual with a password. If the consumer selects automatic, the consumer needs to specify the default payment account. When in automatic mode the proximity payment feature is always active, and the payment application will perform a proximity payment transaction when the consumer waves the phone over a contactless reader. If either of the manual options is selected, the consumer needs to launch the mobile application and needs to choose the pay function to activate the proximity payment feature.

Referring to FIG. 2, the consumer launches the mobile application 302 and selects the proximity payments settings option 304. The consumer has the option of making the account automatic (always on). If the consumer chooses to make the account always on 306, 308, the mobile application sets the configured AID (unique application identifier) to be the default. If the consumer chooses not to make the account automatic, the consumer then has the option of making the account the default payment account when making a manual payment 314, 310, 312.

Referring to FIG. 3, to manually activate the proximity payment feature, the consumer selects a pay or ready-to-pay function within the mobile payment application. This enables the secure element to emulate a contactless card and interact with a contactless reader associated with a POS terminal. This mode remains active until a specified time period has elapsed (the timeout). If the timeout period elapses and the consumer has not conducted a proximity payment transaction, the mobile application deactivates the proximity payment function, requiring the consumer to reactivate it to proceed with the transaction.

The consumer selects the mobile application to launch it and selects the payment function 320, 322. The phone displays the “Ready to Pay” page for 30 seconds or until the consumer exits the page or the payment transaction is completed 324. To proceed with the transaction, the consumer places the phone in the vicinity of a contactless reader 326. The reader obtains the account information from the secure element on the phone and completes the transaction. The phone displays a “Payment Sent” page for 15 seconds or until the consumer exits the page. The phone then reverts to its previous state.

V. Specific Account Management Processes

Referring to FIG. 4, when a message is a transaction receipt, a transaction alert, or a payment-applied message, it is stored in a transaction message repository in the phone. Other messages, such as balance inquiry, balance alert, and payment reminder messages are not stored in the transaction message repository.

Each item in the message repository can correspond to one particular account management event. These events can be supplied OTA as in the case of most alerts and transaction receipts.

The consumer needs to be in the mobile application to access the transaction message repository. The mobile application's main menu provides an option that the consumer can select to open the repository as shown in screen shot 330. The repository displays a list of transaction receipts, transaction alerts, and payment-applied message summaries as shown in screen shot 332.

Referring to FIG. 5, as shown by screen shots 334 and 336, the consumer can view the details of transaction receipts, transaction alerts, and payments that have been applied to the account. Specifically, the consumer can view three different types of transaction messages: transaction receipts, transaction alerts, and payment-applied messages. The content can be different for each type of message. The consumer can select the message and then select the view message option, to display the message detail screen.

Referring to the screen shots 338 and 340 in FIG. 6, a threshold for a transaction alert can be configured within the mobile application. Alternatively, the alert threshold can be configured on the issuer's Web site. If the threshold is surpassed, then a message such as the one shown in screenshot 340 is shown.

Referring to screen shots 342, 344, and 346 in FIG. 7, the consumer can request the existing balance for the credit product that is stored on the mobile phone's secure element. This is similar to typical remote banking functionality except instead of a Web channel, this is for the mobile phone channel.

After the issuer processes the balance inquiry, the issuer transmits the response message to the balance inquiry to the consumer's mobile phone. The balance inquiry is displayed, and also updated in the account summary feature of the mobile application for future reference. The requested balance information includes (1) the issuer's name, (2) current balance, (3) remaining credit available, and (4) disclaimer about the accuracy of balance information for credit accounts.

Referring to screen shots 348, 350, and 352 in FIG. 8, the consumer is able to request the existing balance for the debit product that is stored on the mobile phone's secure element. This is similar to a typical remote banking functionality. The balance inquiry is displayed, and also updated in the account summary feature of the mobile application for future reference. The balance information may include (1) the issuer's name, (2) the current balance in debit account, (3) funds available to withdrawal, (4) available balance, and (5) disclaimer about the accuracy of the balance information.

Referring to the screen shots 354, 356, 358, and 360 in FIGS. 9(a) and 9(b), the consumer can register or unregister for payment reminders using the mobile application. The consumer can configure the current state of the payment reminder feature (ON/OFF).

The consumer does not have to be alerted about whether the configure payment reminder operation with the issuer has been successful. Only the consumer's choices need to be confirmed from within the mobile application at the time these choices are made.

Referring to the screen shots 362, 364, and 366 in FIG. 10, the consumer is able to configure the balance level at which a balance alert occurs. This use case describes this option for the case where the payment instrument is a credit product. The consumer configures the following: (1) The credit balance at which a balance alert will be generated, and (2) the current state of the balance alert feature (ON/OFF).

The consumer does not have to be alerted about whether the configure balance alert operation with the issuer has been successful. Only the consumer's choices need to be confirmed from within the mobile application at the time these choices are made.

Referring to the screen shot 372 in FIG. 11(a), the consumer receives a balance alert for a credit product when a predefined threshold has been exceeded. The issuer generates this alert and it is sent to the consumer's handset.

Referring to the screen shot 374 in FIG. 11(b), the consumer receives a balance alert for a debit product when a predefined threshold has been exceeded. The issuer generates this alert and it is sent to the consumer's handset.

Referring to the screen shot 376 in FIG. 12, the consumer receives an issuer generated risk alert when their payment account has been blocked because of reasons specific to the issuer. The issuer generates this alert and it is sent to the consumer's phone.

Regardless of whether a platform password is configured, the mobile application is launched and the message is displayed to the consumer. Once the message is displayed, the consumer will not be given an option except to acknowledge the message, which exits the application. The message is never stored in some embodiments.

Embodiments of the invention can also include offers as shown by the screen shots 378, 380, and 382 in FIG. 13. First, an offer repository on the phone can be selected as shown in screen shot 378, and the offer repository is opened and offers are checked for expiry. As shown in screen shot 380, different merchants offering different offers can be displayed. The consumer may select one of them and the merchant's specific offer can be displayed. The consumer may thereafter redeem the offer in any number of ways including using the previously described NFC element or contactless element to communicate with a POS terminal.

VI. Multiple Issuer Specific Payment Service Capability

As noted above, the customization and configuration process can include the receipt of data associated with the issuer specific payment application instance, which may be linked to an issuer specific payment service. The data may include computer code for an issuer specific application, code for an issuer specific instance, or code for a link an issuer specific application or instance. For example, in some embodiments of the invention, there may be many different issuer specific payment application instances linked to different issuer specific payment services. The different issuer specific payment services may have different sets of features. For example, one issuer may provide offer messages, and does not provide transaction alert messages. Another issuer may provide transaction alert messages, but does not provide offer messages. In embodiments of the invention, the consumer 10 may select one issuer specific payment service as a default service for use with his phone 10(a), and then may use the phone 10(a) and the selected issuer specific payment service to conduct transactions such as payment transactions. The issuer specific payment services may include specific management or value added services and payment functions.

In some embodiments, once loaded to the device, if not more than one instance exists on the device, then that instance can be the default instance. In other embodiments, multiple payment applications specifically associated with different issuers can be present on the mobile phone. The consumer can select from different issuer specific payment applications as shown in FIG. 14(a) (applications for Bank A, Bank B and Bank C in window 390). Once a payment application is selected (e.g., Bank B in window 392), it can be set as the default payment application as shown in FIG. 14(b).

Referring to the screen shots 402, 404, 406, 408, 410 in FIG. 15, from a usability standpoint, this process strives to achieve the desired result with minimal interaction required from the consumer. It is at the discretion of the issuer to allow consumer configuration and to what level. The consumer interaction is preferably consistent.

Also from a usability standpoint, it is possible that the issuer will not allow the consumer any configuration options. For example, the issuer could configure the platform to be automatically enabled (always on) with free access (that is, no password required). It is also possible that the issuer only allows the consumer to change certain configuration options. For example, the issuer could configure the platform to be manually enabled with mandatory password protected access in which case the consumer would only be prompted to enter a password. In both of the above cases the consumer is always allowed the option to set the platform as the default for proximity.

VII. Computer Apparatuses and Mobile Phones

The various participants and elements in FIG. 1 may operate one or more computer apparatuses to facilitate the functions described herein. Any of the elements in FIG. 1 including the offer engine 18, the messaging gateway 20(a), the issuer 14, the directory services engine 22(a), the service activation system 24(a), and the mobile operator 26 may use any suitable number of subsystems to facilitate the functions described herein. Examples of such subsystems or components are shown in FIG. 16. The subsystems shown in FIG. 16 are interconnected via a system bus 775. Additional subsystems such as a printer 774, keyboard 778, fixed disk 779 (or other memory comprising computer readable media), monitor 776, which is coupled to display adapter 782, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 771, can be connected to the computer system by any number of means known in the art, such as serial port 777. For example, serial port 777 or external interface 781 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus allows the central processor 773 to communicate with each subsystem and to control the execution of instructions from system memory 772 or the fixed disk 779, as well as the exchange of information between subsystems. The system memory 772 and/or the fixed disk 779 may embody a computer readable medium.

FIG. 17 shows a block diagram of another phone 32 that can be used in embodiments of the invention. Such features can be combined with the features shown in the phone 10(a) in FIG. 1. The exemplary wireless phone 32 may comprise a computer readable medium and a body as shown in FIG. 17. The computer readable medium 32(b) may be present within the body 32(h), or may be detachable from it. The body 32(h) may be in the form a plastic substrate, housing, or other structure. The computer readable medium 32(b) may be a memory that stores data (e.g., data relating to issuer specific payment services) and may be in any suitable form including a magnetic stripe, a memory chip, etc. The memory preferably stores information such as financial information, transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. Financial information may include information such as bank account information, bank identification number (BIN), credit or debit card number information, account balance information, expiration date, consumer information such as name, date of birth, etc. Any of this information may be transmitted by the phone 32.

In some embodiments, information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder's account, encrypted PIN, plus other discretionary data.

The phone 32 may further include a contactless element 32(g), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element 32(g) is associated with (e.g., embedded within) phone 32 and data or control instructions transmitted via a cellular network may be applied to contactless element 32(g) by means of a contactless element interface (not shown). The contactless element interface functions to permit the exchange of data and/or control instructions between the mobile device circuitry (and hence the cellular network) and an optional contactless element 32(g).

Contactless element 32(g) is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the phone 32 and an interrogation device. Thus, the phone 32 is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.

The phone 32 may also include a processor 32(c) (e.g., a microprocessor) for processing the functions of the phone 32 and a display 32(d) to allow a consumer to see phone numbers and other information and messages. The phone 32 may further include input elements 32(e) to allow a consumer to input information into the device, a speaker 32(f) to allow the consumer to hear voice communication, music, etc., and a microphone 32(i) to allow the consumer to transmit her voice through the phone 32. The phone 32 may also include an antenna 32(a) for wireless data transfer (e.g., data transmission).

It should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software.

Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.

The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.

One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.

A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary. 

1-21. (canceled)
 22. A method comprising: provisioning, by an over-the-air (OTA) service provider computer to a secure element of a mobile phone, specifications for OTA service activation of a plurality of payment applications by sending data, associated with the plurality of payment applications associated with a plurality of payment services provided by a plurality of issuers, to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal; provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of a mobile application on the mobile phone, an account management event, wherein the mobile phone comprises the secure element storing the plurality of payment applications, and a plurality of mobile applications stored outside of the secure element, wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of payment applications and balance information for at least one of the plurality of payment applications linked to at least one of the payment applications; and sending a plurality of messages from the plurality of issuers to a plurality of mobile applications on the mobile phone.
 23. The method of claim 22, wherein sending the data associated with the plurality of payment applications and sending the plurality of messages are conducted by a mobile operator.
 24. The method of claim 22, wherein the messages in the plurality of messages pass through a messaging gateway.
 25. The method of claim 22, wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message.
 26. The method of claim 22 further comprising, formatting the plurality of messages prior to sending the plurality of messages.
 27. The method of claim 22, wherein the messages are SMS messages.
 28. The method of claim 22, wherein the payment applications respectively perform different sets of services.
 29. The method of claim 22, wherein the mobile phone is able to communicate via near field communications (NFC) with the contactless reader in the point of sale terminal.
 30. The method of claim 22, wherein the mobile phone is able to communicate via near field communications (NFC) with the contactless reader in the point of sale terminal to conduct a payment transaction with the point of sale terminal, the point of sale terminal being at a merchant.
 31. The method of claim 22 further comprising: conducting a payment transaction at the point of sale terminal with the mobile phone using near field communications (NFC).
 32. The method of claim 22, wherein the secure element comprises one of embedded hardware, a removable universal subscriber identity module (USIM), and a removable secure digital (SD) card.
 33. The method of claim 22, wherein an offer message, comprising one of a coupon, a discount, or a promotion selected by a user, is received and stored in an offer repository of the mobile phone.
 34. The method of claim 22, wherein the plurality of mobile applications stored outside of the secure element are configured to register payment reminders.
 35. The method according to claim 22, wherein the over-the-air (OTA) service provider computer is further configured to perform at least one of loading, installing, personalizing, locking, unlocking and removing one or more of the plurality of payment applications on the secure element.
 36. The method according to claim 22, further comprising: receiving an offer message, comprising one of a coupon, a discount, or a promotion selected by a user; storing the offer message in an offer repository of the mobile phone; and in response to expiry of the coupon, the discount, or the promotion, deleting the coupon, the discount, or the promotion from the offer repository of the mobile phone.
 37. A server computer comprising: a processor; and a computer readable medium coupled to the processor, wherein the computer readable medium comprises code executable by the processor to implement a method comprising: provisioning, by an over-the-air (OTA) service provider computer to a secure element of a mobile phone, specifications for OTA service activation of a plurality of payment applications by sending data associated with the plurality of payment applications associated with a plurality of payment services provided by a plurality of issuers to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal; provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of a mobile application on the mobile phone, an account management event, wherein the mobile phone comprises the secure element storing the plurality of payment applications, and a plurality of mobile applications stored outside of the secure element, wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of payment applications and balance information for at least one of the plurality of payment applications linked to at least one of the payment applications; and sending a plurality of messages from the plurality of issuers to the plurality of mobile applications on the mobile phone.
 38. The server computer of claim 37, wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message.
 39. A system comprising: a first server computer comprising a first processor and a first computer readable medium comprising code, executable by the first processor to format a plurality of messages from a plurality of issuers; and a second server computer coupled to the first server computer, wherein the second server computer is an over-the-air (OTA) service provider computer, the second server computer comprising a second processor, and a second computer readable medium coupled to the second processor, wherein the second computer readable medium comprises code executable by the second processor to implement a method comprising: provisioning to a secure element of a mobile phone specifications for OTA service activation of a plurality of payment applications by sending data associated with the plurality of payment applications associated with a plurality of payment services to a mobile phone comprising a contactless element, which is capable of allowing the mobile phone to communicate contactlessly with a contactless reader in a point of sale terminal; provisioning, by the over-the-air (OTA) service provider computer to a transaction message repository of an mobile application on the mobile phone, an account management event, wherein the mobile phone comprises the secure element storing the plurality of payment applications, and a plurality of mobile applications stored outside of the secure element, wherein the secure element is managed by the OTA service provider and comprises hardware configured to securely store the plurality of payment applications and balance information for at least one of the plurality of payment applications linked to at least one of the mobile applications; and sending the plurality of messages from the plurality of issuers to the plurality of mobile applications on the mobile phone.
 40. The system of claim 39, wherein the first server computer is operated by a messaging service provider and the second server computer is operated by a mobile network operator.
 41. The system of claim 39, wherein the plurality of messages comprise two or more of a balance alert configuration response message, a balance alert message, a balance inquiry response message, a payment applied message, a payment reminder configuration response message, a payment reminder message, a transaction alert configuration response message, or a transaction alert message. 